Obsolete dead sdks #2984
Obsolete dead sdks #2984
Conversation
Explain please? It is supposed to lead to #2788 which is a PR containing the notice "🎩 Website & Content WG". Admittedly we might update it to a PR that uses the complete current template.
Should this be a draft PR then? |
good point, i forgot those existed
it didnt feel very intentional to link to a PR about a11y in images in context of COI notices? |
CoI is one out of many concerns. Sometimes it's just context of why someone is doing something, or on whose authority. Would you be happier with #2969 as an example? -> moved to https://github.com/matrix-org/matrix.org/pull/2979/files#r2473508377 |
|
Ping list for awareness: |
|
Oop, CI failed because it couldnt mark this PR as draft due to not including comments in the markdown... lol |
|
Thanks for the ping! I'm still involved with the Elm SDK! For better of for worse, it's very common for Elm packages to not get any updates very frequently. Aside from 6 commits in the past few months, the Elm compiler itself hasn't had any Git activity for two years, nor has it had any substantial changes since 2021. Git activity isn't a good metric for code quality in Elm. The most popular UI library hasn't had any updates in 4 years, the stdlib http library that the Elm SDK relies on is unchanged since 6 years and there are many other examples of Elm libraries that work reliably despite seeing few updates. The Elm SDK is the same. It's not under active development but it still works. (Behind the scenes I've recently started working on a new major version that reorganizes the library's API, despite its development process is slowed down by other Matrix-related projects that I'm committed to.) I'm monitoring for bug reports, and the SDK is still functional & operational. |
|
It wasn't really a question of code quality, and i do agree that git activity may not be the best indicator, though i did check for alternate branches for activity to avoid situations like this ^^' I wouldn't expect many outdated SDKs to actually break, but more lacking in modern things that may have changed (ie. auth media, no more reply fallbacks, all the room v12 changes etc, just to name a few from relatively recent times). Most of the entries on this list seem to be outright inactive or deprecated, and I was aiming to bring the matrix.org listing more in line with that. Good to hear that the Elm SDK is still maintained, I'll be dropping the commit for marking the Elm SDK as such :) |
Signed-off-by: Rory& <[email protected]>
…years) Signed-off-by: Rory& <[email protected]>
Signed-off-by: Rory& <[email protected]>
Signed-off-by: Rory& <[email protected]>
Signed-off-by: Rory& <[email protected]>
Signed-off-by: Rory& <[email protected]>
Cosium/matrix-communication-client@ecb4f5f (2023 - last code change) Cosium/matrix-communication-client@ed34389 (2025 - only new human commit since 2023, only makes a ci change) Signed-off-by: Rory& <[email protected]>
TheArcaneBrony
force-pushed
the
obsolete-dead-sdks
branch
from
4a2fbf8 to
57f4948
Compare
Signed-off-by: Rory& <[email protected]>
Waiting to DM cvwright Signed-off-by: Rory& <[email protected]>
Signed-off-by: Rory& <[email protected]>
TheArcaneBrony
force-pushed
the
obsolete-dead-sdks
branch
from
57f4948 to
464f18a
Compare
|
^ (Rebased on main first, and then dropped the elm deprecation commit, hence 2 force pushes) |
3 participants
Marked all SDKs under ecosystem with no new commits for over a year as obsolete.
Also fixes the git url for matrix.swift and qt version for quotient.
Please check commitlog (+description) since some commits may be dropped later as i'm awaiting maintainer respones (elm sdk @ 11 months, matrix.swift @ 9 months)
Also did not touch
matrix-mellifluousness/sdkdespite inactivity for 2 years, hmu if you'd like me to obsolete it for consistency.Related issues: #1584
Contributing in a specific role: your link is broken btw :)
In any case, I had originally started checking C# SDKs, which I suppose may have a COI as I'm maintaining Rory&::LibMatrix
✔️ Checklist
<>to linkify them (learn more).[label](@/target.md)syntax./blogpage, especially for multiple posts on the same day. Prefer UTC format, e.g.2025-12-01T14:00:00Zfor Dec 1st, 2025, 2pm UTC.